How to implement Background jobs in ASP.NET?

Question

ICSM · Answer

In ASP.NET (especially MVC 5 / Web API – non-Core), background jobs are used to run
long-running or non-blocking tasks such as emails, reports, queue processing, cleanup jobs, etc.,
without blocking HTTP requests.
Below is a clear, production-oriented guide, from simple → advanced.
1. When Do You Need Background Jobs?
Use background jobs when:
Sending emails / SMSFile processing (PDF, Excel, images)Scheduled tasks (daily reports)Bulk notificationsRetryable or delayed workQueue-based processing
Do NOT run these directly inside controller actions.
2. What NOT to Do (Common Mistake)
public ActionResult SendEmail()
{
    SendEmailLogic(); // Blocks request thread
    return View();
}
Problems:
Request timeoutApp pool recycle kills taskPoor scalability
3. Option 1: Fire-and-Forget (Very Basic – Not Reliable)
Task.Run(() =andgt; SendEmailLogic());
Use only for demos or internal tools
Issues:
App recycle kills taskNo retryNo monitoring
4. Option 2: Background Worker Using HostingEnvironment.QueueBackgroundWorkItem
Recommended for ASP.NET MVC 5
Example
public ActionResult SendEmail()
{
    HostingEnvironment.QueueBackgroundWorkItem(ct =andgt;
    {
        EmailService.Send();
    });
    return Content("Email queued");
}
Advantages
Survives request completionUses ASP.NET-managed threads
Limitations
App pool recycle still kills jobsNo persistenceBest for:
Short background work (seconds)
5. Option 3: Windows Service (Most Reliable)
Best for heavy / critical jobs
Architecture
ASP.NET App → Database / Queue → Windows Service
Flow
Web app inserts job into DB / queueWindows Service polls and processes jobsSupports retry, logging, rate limiting
Example Job Table
CREATE TABLE BackgroundJobs (
    Id BIGINT IDENTITY,
    JobType NVARCHAR(50),
    Payload NVARCHAR(MAX),
    Status INT,
    RetryCount INT,
    CreatedOn DATETIME
)
Windows Service Loop
while(true)
{
    var jobs = GetPendingJobs();
    ProcessJobs(jobs);
    Thread.Sleep(5000);
}
Survives IIS recycleCan scale independentlyProduction-grade
6. Option 4: Hangfire (Most Popular and Easiest)
Highly recommended for ASP.NET MVC
Install
Install-Package Hangfire
Install-Package Hangfire.SqlServer
Configure (Global.asax)
Hangfire.GlobalConfiguration.Configuration
    .UseSqlServerStorage("DefaultConnection");
app.UseHangfireServer();
app.UseHangfireDashboard();
Create Background Job
BackgroundJob.Enqueue(() =andgt; EmailService.Send());
Scheduled Job
RecurringJob.AddOrUpdate(
    "daily-report",
    () =andgt; ReportService.Generate(),
    Cron.Daily);
Features
Persistent jobsRetry automaticallyDashboard UIDelayed and recurring jobs
Excellent for emails, reports, queues
Production-ready
Minimal code
7. Option 5: Queue-Based Background Processing (Advanced)
Architecture
Client → API → Queue → Worker
Queues:
SQL QueueRabbitMQAzure Service BusAmazon SQS
Example (DB Queue)
INSERT INTO MailQueue (Email, Status) VALUES (...)
Worker:
var mail = GetPendingMails();
SendMail(mail);
MarkCompleted();
Best for high-volume systemsSupports scaling and retriesDecoupled design
8. Comparison Table
Approach
Reliability
Retry
Best For
Task.Run
NO
NO
Demo only
QueueBackgroundWorkItem
Sometime
No
Short tasks
Hangfire
Yes
Yes
Most apps
Windows Service
Yes
Manual
Heavy jobs
Message Queue
Yes
Yes
Large systems
9. Best Practices (Very Important)
Keep jobs idempotentImplement retry with backoffLog job executionRate-limit background jobsNever rely on IIS uptime aloneSeparate job execution from HTTP lifecycle
10. Recommended Setup (Real World)
For ASP.NET MVC 5 production apps:
Hangfire + SQL Server
Windows Service for heavy workloads
Queue-based architecture for scale
and

forum

How to implement Background jobs in ASP.NET?

Anubhav Kumar

Can you answer this question?

1 Answers

1. When Do You Need Background Jobs?

2. What NOT to Do (Common Mistake)

3. Option 1: Fire-and-Forget (Very Basic – Not Reliable)

4. Option 2: Background Worker Using `HostingEnvironment.QueueBackgroundWorkItem`

Example

Advantages

Limitations

5. Option 3: Windows Service (Most Reliable)

Architecture

Flow

Example Job Table

Windows Service Loop

6. Option 4: Hangfire (Most Popular & Easiest)

Install

Configure (Global.asax)

Create Background Job

Scheduled Job

Features

7. Option 5: Queue-Based Background Processing (Advanced)

Architecture

Example (DB Queue)

8. Comparison Table

9. Best Practices (Very Important)

10. Recommended Setup (Real World)

Liked By

Approach	Reliability	Retry	Best For
Task.Run	NO	NO	Demo only
QueueBackgroundWorkItem	Sometime	No	Short tasks
Hangfire	Yes	Yes	Most apps
Windows Service	Yes	Manual	Heavy jobs
Message Queue	Yes	Yes	Large systems